Method and system for managing utilization of slices in a virtual network function environment

ABSTRACT

Aspects of the subject disclosure may include, for example, determining a first group of virtual network functions of a first network slice instantiated within a software defined network and adapted to perform a first activity that facilitates delivery of a service to wireless equipment of a first user. An occurrence of a condition is determined and in response, access is facilitated to a second group of virtual network functions of a second network slice. The second group of virtual network functions, when instantiated within the software defined, network are configured to deliver the service to the wireless equipment of the first user during the occurrence of the condition within the first network slice. The second network slice is further adapted to perform another activity that facilitates delivery of another service during an occurrence of another condition within another network slice. Other embodiments are disclosed.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.15/658,595, filed Jul. 25, 2017, which is hereby incorporated herein byreference in its entirety.

FIELD OF THE DISCLOSURE

The subject disclosure relates to a method and system for managingutilization of slices in a virtual network function environment.

BACKGROUND

According to virtual network function (VNF) architectures, such as 5Gnetworks, services are handled by decentralized VNFs that areinstantiated either for a specific service or group of services. In atlast some instances, the instantiated VNFs can be reused, depending oncertain parameters such as capacity, quality of service (QoS), location,etc. These groups of decentralized VNFs can be referred to as “slices”of the network. As the name eludes to, network slices are parts of a3^(rd) Generation Partnership Project (3GPP) 5G network that arespecifically instantiated for certain services. There are number ofslices in the network depending on the location such as a dedicatedslice relatively close to a large customer enterprise or high-QoS slicefor a premium service. These slices can be part of a cloud networkrunning on a default hardware with a given limitations such as number ofdedicated processors and memory, etc. The use, sharing and re-use ofslices promotes an efficient utilization of the underlying physicalnetwork resources.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference will now be made to the accompanying drawings, which are notnecessarily drawn to scale, and wherein:

FIG. 1 depicts an illustrative embodiment of an example communicationnetwork for providing services to communication devices;

FIG. 2 depicts an illustrative embodiment of another examplecommunication network for providing services to communication devices;

FIGS. 3A-3B depicts illustrative embodiments of processes for managingnetwork resources used in portions of the system described in FIGS. 1and 2;

FIGS. 4-5 depict illustrative embodiments of communication systems thatprovide media services that can be used by the communication networks ofFIGS. 1-2;

FIG. 6 depicts an illustrative embodiment of a web portal forinteracting with the communication systems of FIGS. 1-2, and 4-5;

FIG. 7 depicts an illustrative embodiment of a communication device; and

FIG. 8 is a diagrammatic representation of a machine in the form of acomputer system within which a set of instructions, when executed, maycause the machine to perform any one or more of the methods describedherein.

DETAILED DESCRIPTION

The subject disclosure describes, among other things, illustrativeembodiments for dynamic assignment of specialized network slicesincluding groups of VNFs that perform or otherwise support performanceof rigorous activities generally beyond the scope of dedicated slicesincluding different groups of VNFs. Such specialized slices can bereferred to as special or super slices. Super slices can provide extracapabilities, e.g., on demand, that extend beyond designatedperformance, and in at least some instances, beyond capabilities ofnormally provisioned or dedicate slices. The extra capabilities of thesuper slice can address exceptions that may occur during which thededicated slices are unable to accommodate full renderings of theirrespective services. Other embodiments are described in the subjectdisclosure.

One or more aspects of the subject disclosure include a device,including a processing system including a processor, and a memory thatstores executable instructions. The instructions, when executed by theprocessing system, facilitate performance of operations, includingidentifying a first group of virtual network functions instantiatedwithin a software defined network and adapted to perform a firstactivity that facilitates delivery of a dedicated service to wirelessequipment of a first user under normal conditions. An occurrence isdetected of a condition whereby delivery of the dedicated service to thewireless equipment of the first user requires a second activity, whereinthe first group of virtual network functions is not designated toperform the second activity. Access to a second group of virtual networkfunctions is facilitated responsive to the detecting of the occurrenceof the condition. The second group of virtual network functions wheninstantiated within the software defined network are adapted to performthe second activity that facilitates delivery of the dedicated serviceto the wireless equipment of the first user during the occurrence of thecondition.

One or more aspects of the subject disclosure include a process,including determining, by a processing system including a processor, afirst group of virtual network functions instantiated within a softwaredefined network and adapted to perform a first activity that facilitatesdelivery of a dedicated service to wireless equipment of a first userunder normal conditions. An occurrence of a condition is detected by theprocessing system, whereby delivery of the dedicated service to thewireless equipment of the first user requires a second activity, whereinthe first group of virtual network functions is not designated toperform the second activity. Access to a second group of virtual networkfunctions is facilitated, by the processing system and responsive to thedetermining of the occurrence of the condition. The second group ofvirtual network functions when instantiated within the software definednetwork are adapted to perform the second activity that facilitatesdelivery of the dedicated service to the wireless equipment of the firstuser during the occurrence of the condition.

One or more aspects of the subject disclosure include a machine-readablestorage medium, including executable instructions that, when executed bya processing system including a processor, facilitate performance ofoperations. The operations include determining a first group of virtualnetwork functions instantiated within a software defined network andadapted to perform a first activity that facilitates delivery of adedicated service to wireless equipment of a first user under normalconditions. An occurrence of a condition is determined whereby deliveryof the dedicated service to the wireless equipment of the first userrequires a second activity, wherein the first group of virtual networkfunctions is not designated to perform the second activity. Access to asecond group of virtual network functions is facilitated, responsive tothe determining of the occurrence of the condition. The second group ofvirtual network functions when instantiated within the software definednetwork are adapted to perform the second activity that facilitatesdelivery of the dedicated service to the wireless equipment of the firstuser during the occurrence of the condition.

In a virtual network function (VNF) environment, one or more VNFs takeon responsibilities of handling network functions that run on one ormore virtual machines (VMs) on top of hardware of a physical networkinginfrastructure, such as routers, switches, etc. It is understood thatthe disclosure provided herein can apply, without limitation, to any VNFenvironment. The various examples disclosed herein related to so-called3GPP 5G network services. In particular, the 5G network services can behandled by one or more virtual network functions that can bedecentralized. Alternatively or in addition, the one or more virtualnetwork functions can be instantiated for a specific service or group ofservices. In at least some embodiments, one or more of the virtualnetwork functions can be reused, e.g., depending up on certainparameters such as capacity, QoS, location, e.g., of wirelesscommunication equipment supported by the 5G network, and the like.

Different groups of VNFs, which may be decentralized, are sometimesreferred to as “slices” of the network. Generally speaking, a particularslice relates to a portion of a 5G wireless mobile network specificallyinstantiated for a particular service or group of services. It isunderstood that in any practical 5G application, there may be a numberof slices in the network depending upon a location(s) one or more ofsupported wireless communication equipment. For example, a dedicatedslice can be instantiated for a customer enterprise, e.g., in relativelyclose physical and or network proximity to a large customer enterprise.Alternatively or in addition, a dedicated slice can be instantiated toprovide a relatively high QoS, e.g., in association with a premiumservice, a premium level of subscription, and the like. In at least someembodiments, one or more of the slices are part of a cloud network. Itis understood that a cloud network can be adapted to run physicalresources, such as default hardware, which generally presences at leastsome limitations, such as number(s) of dedicated processors, class(es)of physical processors, memory size and/or type, storage and the like.

As slices are generally associated related tasks and/or activities, itis understood that the slice(s) can be configured and/or otherwisedefined in association with a predetermined scope and/or technicalrequirement. The scope and/or technical requirement can be a defaultvalue, e.g., according to one or more of a class of user and/or a classor type of equipment of the user, a level of subscription associatedwith the user, a class and/or type of service, function, and the like.Accordingly, a VNF, when instantiated, is adapted to perform and/orotherwise provide the tasks and/or activities according to thepredetermined scope and/or technical requirement.

In at least some scenarios, a predetermined scope of a network slice canbe considered, without restriction, as a capacity value. It isunderstood that in any practical realization, a demand upon resources ofthe network slice can vary and/or otherwise fluctuate. Such variationsand/or fluctuations can result from one or more of a requirement of atype of service supported by the network slice, a location of thewireless equipment associated with the network slice, an environmentalcondition, a condition of the network, a request and/or requirement ofone or more of the mobile network service provider, a third-partyservice provider, equipment of the user, and/or another entity, such asa network operation and maintenance entity, an enterprise customer, athird-party entity, e.g., a government entity, and the like.

By way of non-limiting example, one or more slice(s) are associated witha particular activity, such as a calculation requiring an orchestrationof a repository. It is understood that such in-scope services caninclude calculations requiring orchestration of up to some maximumnumber of repositories. Accordingly, one or more VNFs of the group ofVNFs of the associated slice(s) are configured or otherwise adapted toaccommodate the in-scope services. It is further understood that undersome circumstances, it may be advantageous and/or necessary for theservices to require orchestration a relatively large orchestration ofrepositories, e.g., larger than those anticipated or otherwiseassociated with the in-scope services. According to the techniquesdisclosed herein, so-called out-of-scope or special activities can beaccommodated and/or otherwise serviced based one or more other slices,e.g., including one or more other groups of VNFs that aredistinguishable from slice(s) and/or VNFs supporting in-scopeactivities. These other slices are referred herein to as special slicesand/or super slices. The super slices can perform and/or otherwisesupport one or more functions and/or services, such as one or more of aprocessing capacity, a memory capacity, a communication capacity, astorage capacity, and the like, on an as-need and/or on-demand manner tofacilitate delivery of a service to the equipment of a user duringperiods of exceptional and/or rigorous activity. In at least someembodiments, a super slice can be located anywhere on a network. Forexample, in 5G examples, the super slice and can be reached and/orotherwise accessed by way of a default slice and/or a managing gateway(mGW).

Beneficially, the super slice models disclosed herein allow dedicatedslices to be sized according to an anticipated capacity, rather than apeak capacity. The super slices can provide services to accommodate peakcapacity in total and/or above the anticipated or design capacity ofdedicated slices. Accordingly, network resources of the super slice areemployed when needed without having to sit idle during periods of normaloperation. To the extent peak demands of different services occur atdifferent times and/or locations, it is understood that common networkresources, e.g., according to the super slice, can support multipleservices and/or applications. To the extent multiple services orapplications encounter overlapping peak demands, it is understood thatthe super slice can include some measure of elasticity. For example, thesuper slice can include a scalable model that can be scaled based on oneor more of network conditions, requests for super slice support and thelike.

In general, network slices can be identified, instantiated and/orotherwise created to facilitate services utilized by individualsubscribers and/or subscribers of enterprises clients, such as largebusiness, governmental organizations, social groups, e.g., affinitygroups, and the like. These slices are generally adapted or otherwiseconfigured to perform a particular task or group of tasks. It isunderstood that in at least some embodiments, the task(s) can dependupon one or more of a location, e.g., location of the equipment of thesubscriber and/or a location of the enterprise client, a QoS and/or acapacity of a particular service. In at least some embodiments, slicesof the network are combinations of VNFs instantiated by a serviceorchestration manager. The slice(s) can be instantiated on defaulthardware in order to reduce network complexity and/or to realize capitalsavings, e.g., on proprietary hardware and/or software. However, withinany service infrastructure there may be exceptions whereby a slicecapability will not accommodate a full rendering of a particularservice.

For such unlikely and/or infrequent situations and/or scenarios, e.g.,in case of an emergency and/or need to perform a very specializedactivity such as large calculation of data with in number of data bases,one or more super slices, one or more activities can be assigned to oneor more other slices, e.g., super slice(s). In at least someembodiments, the super slice(s) are instantiated to serve existingslices. For example, the super slice(s) can be dynamically assigned toperform specific tasks depending one or more of a priority,availability, network condition(s), user equipment type, subscriptionlevel(s), service type(s), location(s), and the like.

For example, while a particular service is running within apredetermined slice of a network and an emergency situation occurs, ahigher and/or greater capacity and/or performance may be necessary tocontinue provision of the particular service. In order to continueproviding the particular service, it may be necessary to expand and/orprovision one or more premium and/or emergency services, at least duringthe occurrence of the special, e.g., an emergency situation. At leastone example of a special situation includes a security attack, e.g.,based on a distributed denial of service (DDoS) attack, or a heightenedsecurity requiring more intense computational processing.

FIG. 1 depicts an illustrative embodiment of another examplecommunication network 100, e.g., a 3GPP 5G network adapted to provideservices to equipment of users or subscribers. In this example, theequipment includes wireless devices, such as a smart phone and/or tabletdevice 104 a, an intelligent home or building controller, such as asmart thermostat 104 b, a surveillance monitor 104 c and/or a smarttelevision 104 d, generally subscriber equipment 104. It is understoodthat the user equipment can include mobile communication devices,wireless devices that may be mobile or stationary, e.g., smart utilitymeters of a building including a mobile cellular radio, and in at leastsome instances, wired devices, such as cable television, a satellitereceiver, and/or other network accessible devices connected to physicalnetwork resources, and the like.

The subscriber equipment 104 can access resources of the 5G network byway of a radio access network (RAN) 105. The RAN 105 can include awireless access terminal 108, such as that associated with a relativelylarge cell, e.g., a macro cell, and/or a relatively small cell, e.g., apicocell and/or femtocell. For example, the wireless access terminal 108can include an evolved NodeB (eNB) adapted to support 4G and/or 5Gprotocols. For 5G applications, the eNB is sometimes referred to as a“gNB” 108. The gNB 108 is in communication with extended resources ofthe 5G network 102, e.g., by way of a backbone network 109. In at leastsome instances, the RAN 105 and/or the wireless access terminal 108support non-licensed frequency spectrum operations, e.g., accordingnon-5G technologies, such as Wi-Fi and/or Bluetooth.

The example 5G network includes a default slice 110. The default slicecan provide independent processing of control plane messages and userplane messages, e.g., to coordinate access to dedicated slices,services, applications, mobility, and so on. In many applications, adefault slice 110 is established in association with a particular userdevice and/or group of user devices, e.g., upon discovery of and/orattachment of the device(s) to the network. In at least some sense, thedefault slice can be analogized to a default bearer of a 3GPP 4Gnetwork. This may occur when a subscriber equipment 104 is first poweredon, transitions from a dormant mode to an active mode and/or as a resultof mobility of the device 104 to within a region of coverage of thewireless access terminal 108. It is understood that the subscriberequipment 104 can operation in association with one or more services,applications and/or functions accessible via the 5G network 102. Theservices can include, without limitation, streaming audio services,e.g., streaming music services, interactive voice over IP (VoIP),streaming video, telephone, short message service, access to the WorldWide Web (WWW), file transfer, cloud storage, social networking, gaming,home and/or building automation, home and/or building security, medicalmonitoring, emergency services, and so on.

In at least some embodiments, the network 102 includes one or morededicated slices, e.g., slice_X 112 a, slice_Y 112 b, and slice_Z 112 c,generally 112. The dedicated slices 112 can be established on one ormore of a per-service basis and/or a per-subscriber basis. The dedicatedslices 112 can be provisioned for individual users and/or classes ofusers, e.g., according to one or more of a subscription level, asubscriber equipment type, a location, an association, e.g., an employeeof an enterprise subscriber, a network condition and so on. In thismanner, it is foreseeable that at least some of the dedicated slices 112can be shared. AT least some of the dedicated slices include one or morefunctional modules or agents, such as a authentication and/or accessmodule 120, a mobility module 122, a common control plane processingmodule 124, and a network slice selection function 128.

The default slice 110 and/or dedicated slices 112 can include one ormore functions. By way of example, the default slice 110 includes commonfunctions 130 that can include functions implementing an mGW 132, and/ora slice selection function (SSF) 134. The mGW 132 can include functionssupporting 5G networking, as generally understood by those familiar withthe principles of 3GPP 5G, alone or in combination with otherfunctionality disclosed herein, e.g., in association with access tosuper slices. In some embodiments, the SSF 134 can facilitate access toone or more of the dedicated slices 112. Alternatively or in addition,the SSF 134 can facilitate access to one or more super slices 140.

The illustrative example includes one super slice 140. It is understoodthat the network can instantiate one or more super slices 140, e.g., inresponse to one or more of anticipated demand, actual demand, networkconditions, environmental conditions, user requests, service providerrequests, equipment requests, and the like. The super slice 140 can beconfigured to provide, support and/or otherwise facilitate a particularservice, task, activity, and the like. Alternatively or in addition, thesuper slice 140 can be configured to provide one or more generalservices, tasks, activities, and the like, such that the same superslice 140 can service demand and/or request from a variety of differentdedicates slices 112.

The illustrative super slice 140 includes access modules or agents, 142a, 142 b, 142 c, 142 d, generally 142. The access modules 142 canperform one or more of authentication and/or authorization of requeststo the super slice 140. Without restriction, it is understood thataccess to the super slice 140 can depend on one or more of subscriptionlevel, network conditions, nature of the request, priority of therequest, locations, times of day/days of week, and so on.

In some embodiments, one or more of the dedicated slices 112 facilitatedelivery of a premium service of function to the subscriber equipment104. In the illustrative example, the network 102 includes a premiumservice 106 including one or more premium functions 114 and/or one ormore virtual repositories 116. The premium service is generally wellunderstood such that provisioning of the associated dedicated slice_X112 a allocates sufficient VNFs to accommodate access to and/or deliveryof the service 106. In at least some instances, special circumstancesare detected by way of one or more of the dedicated slice 112 and/or thepremium service 106.

In the illustrative example, the user equipment 104 establishes accessto regular service, e.g., “business as usual,” by way of the defaultslice 110 and one or more of the dedicated slices 112. According to theillustrative example, business as usual can include access to one ormore premium functions 114 and/or virtual repositories 116 of a premiumservice 106 by way of the default slice and the dedicated slice. A firstline, labeled “1” is illustrated between the user equipment 104 and thededicated slice 112 by way of the default slice 110. It is determined,e.g., by one or more of the default slice 110, the dedicated slice 112a, the premium service 106 and/or some other entity, that the capacityof the existing slices 110, 112 a is insufficient. Namely, anexceptional requirement for access to resources beyond those allocatedis determined. To the extent the determination is made by the premiumservice 106, e.g., by detecting and/or otherwise identifying anemergency situation, the condition and/or request is conveyed to thededicated slice 112. A dashed arrow labeled “2” indicative of themessage exchange is illustrated between the premium service 106 and thededicated slice 112 a.

The dedicated slice 112 a, e.g., by way of the NSSF 128 and/or the CCPSE124, generates and/or passes along a request for accessing the superslice 140, e.g., as a dedicated high performance slice. The request isfirst passed to the common functions 130 of the default slice 110, e.g.,according to a dashed line labeled “3.” Continuing with the illustrativeexample, the mGW 132 sends a request to the super slice 140 and/or anSDN controller and/or orchestrator for accessing, e.g., by way ofleasing a right to use the super slice 140. A line between the commonfunctions 130 and the super slice 140, labeled “4”

According to a policy, a business rule and/or another parameter accessto the super slice 140 granted and new connection to super slice 140 issetup, e.g., according to dashed line between the default slice 110 andthe super slice 140. In at least some embodiments, resources of thesuper slice 140 can be “chained” and/or otherwise associated with adedicated slice 112. In the illustrative example, resources of the superslice 140 are chained to the dedicated slice 112 a associated with thepremium service 106 responsible for the exceptional condition. A dashedline extending from the default slice 110 to the dedicated slice 112 aby way of the super slice 140 labeled “6” represents the chainedassociation.

Upon a completion and/or resolution of the exceptional conditions, it isunderstood that the network 102 can return to a normal configuration,e.g., releasing the super slice 140. Accordingly, the super slice can bereserved as a resource to serve requests from other premium services106, other dedicated slices 110, other devices 104, and/or futurerequests from the same premium service 106, dedicated slice 110, and/ordevices 104.

In at least some embodiments an mGW of a 5G network provides a requestfor leasing a right to access and/or otherwise use a super slice. Accessto the super slice can be granted according to one or more of a policy,a business rule and/or another parameter. Once granted, a new connectionto can be set up to access resources of the super slice. It isunderstood that the super slice can be located anywhere on the network.As disclosed in more detail below, the super slice can be reached by adefault slice and/or an mGW. Without restriction, the mGW can grantaccess to super slices on demand, e.g., according to one or more of aservice level agreement (SLA), smart billing (dedicated service chargesdifferently when Super slice used depending of supply and demand of thesuper slice capacity and availability. In at least some embodiments, themGW can create additional capacity, e.g., depending upon one or more ofpolicy and preferences, by reducing other services usage of the serviceslice.

Beneficially, dynamic allocation of a special, e.g., a super, slice, canreduce an overall cost capital expenditure and/or operationalexpenditure. The savings can be realized by way of a core network thatprovides relatively simple network slices, e.g., provisioned withoutregard to any unlikely, special and/or sparsely required resources. Thiscan be accomplished, as disclosed herein, by provisioning networkcomplexity through assignment of more complex tasks to one or more superslices. For instance, if there is super security slice, there is no needto add every permutation of security algorithms into every slice. Inaddition to a reduction of cost of network operation and maintenance,equipment of subscribers enjoy access to special capabilities andqualities of all the services across the network, e.g., for exceptionalsituations, by granting access to super slices.

Referring now to FIG. 2, illustrative embodiments of an exemplarycommunication network for providing services to communication devices isshown. In one or more embodiments, a communications system 200 caninclude a Software Defined Network (SDN), or SDN Network 250. The SDNNetwork 250 can be controlled by one or more SDN Controllers. Forexample, the SDN network 250 can include a manager SDN controller 230,an access SDN controller 235, a Core SDN controller 240, and/or atransport SDN controller 245. The functions of the different types ofSDN Controllers 230-245 are further described below. Each SDNcontroller, such as, for example and ease of illustration, the managerSDN controller 230, can be provided by a computing system executingcomputer-executable instructions and/or modules to provide variousfunctions. In one or more embodiments, multiple computer systems orprocessors can provide the functionality illustrated and describedherein with respect to each SDN controller 230-245. To simplify thedescription of the concepts and technologies described herein, each SDNcontroller 230-245 is illustrated and described herein as being providedby a single computing system. However, it should be understood that thisexample is illustrative and therefore should not be construed as beinglimiting in any way.

In one or more embodiments, each SDN controller 230-245 can includevarious components and/or can be provided via cooperation of variousnetwork devices or components. For example, each SDN controller 230-245can include or have access various network components or resources, suchas a network resource controller, network resource autonomouscontroller, a service resource controller, a service controlinterpreter, adapters, application programming interfaces, compilers, anetwork data collection and/or analytics engine. Each SDN controller230-245 also can include or access information describing availableresources and network information, such as network object statistics,events or alarms, topology, state changes. In one or more embodiment,each SDN controller 230-245 can use and/or can generate and/or accesssystem configurations, including configurations of resources availableto the manager SDN controller 230 for proving access to services.

In one or more embodiments, the communication system 200 can include aservice-supporting portion, referred to generally as a service layer225. The service layer 225 can provide access to services and/orapplications, e.g., including third-party services and/or applicationsat a higher application layer. The service layer 225 may includecapability servers, e.g., owned by or otherwise under the direction ofan operator of the communication network 200, that can access andprovide access to application layer servers, e.g., including applicationlayer servers owned by third-party content providers via open and/orsecure Application Programming Interfaces (APIs). Alternatively or inaddition, the service layer 225 can provide an interface to a coreportion of the network referred to generally as a core network. Thecommunication network 200 can also include access to applications, suchas fixed applications and mobile applications 262A-C.

In one or more embodiments, the communication network 200 can include anSDN network 250. The SDN network 250 can include one or more SDNcontrollers 230, 235, 240 and 245 that can provide different types offunctions and can be arranged in virtual layers. For example, the SDNnetwork 250 can include a manager SDN controller 230 that controls andcoordinates functioning of the SDN network 250. The manager SDNcontroller 230 can be a top-level management system in the architecture.Below the manager SDN controller 230, a next level of SDN controllers235, 240 and 245 can be instantiated and configured by the manager SDNcontroller 230 to provide specific classes of functionality in thearchitecture. For example, the manager SDN Controller 230 can providelevel-3 functionality to control and coordinate service control,configuration, and data flow in the communication network 200. Themanager SDN controller 230 can, as needed, instantiate, configure,and/or direct level-2 SDN controllers 235, 240 and 245 for controllingaccess, core, and/or transport capabilities in the communication network200.

In one or more embodiments, the SDN network 250 can allow thecommunication network 200 to separate control plane operations from adata plane operations and can enable layer abstraction for separatingservice and network functions or elements from physical networkfunctions or elements. In one or more embodiments, the manager SDNcontroller 230 can coordinated networking and provision of applicationsand/or services. The manager SDN controller 230 can manage transportfunctions for various layers within the communication network and accessto application functions for layers above the communication network. Themanager SDN controller 230 can provide a platform for network services,network control of service instantiation and management, as well as aprogrammable environment for resource and traffic management. Themanager SDN controller 230 also can permit a combination of real timedata from the service and network elements with real-time or nearreal-time control of a forwarding plane. In various embodiments, themanager SDN controller 230 can enable flow set up in real-time, networkprogrammability, extensibility, standard interfaces, and/or multi-vendorsupport. In one embodiment, interactions between layers of thecommunication network 200 can be based upon policies to determineoptimum configuration and rapid adaptation of the network 200 tochanging state and changing customer requirements for example, predicteddemand, addition of new users, spikes in traffic, planned and unplannednetwork outages, adding new services, and/or maintenance.

In one or more embodiments, each SDN controller 230-245 can instantiatea virtualized environment including compute, storage, and data centernetworking for virtual applications. For example, the manager SDNcontroller 230 can direct on-demand instantiation of network elements,such as Virtual Network Function (VNF) elements at on-demand locationsto support network services for a customer or for the autonomous networkresource controller where capacity is needed or where backup of networkelements due to failures. Service functions can be moved and/or changedin response to traffic flow rather than traffic flow moving to thedesired service functions.

In one or more embodiments, the manager SDN controller 230 can cooperatewith a cloud orchestrator in instantiating level-2 SDN controllers235-245 and network services to support the network configuration inconnecting Virtual Machined (VMs) that the cloud orchestrator is settingup. The network instantiation and configuration can includeconfiguration of the virtual networks, which may operate at variousphysical levels in a cloud server architecture, including hypervisor,top of rack, cloud network fabric, and/or IP provider edge, which canconnect the cloud network with the service provider WAN network. In oneor more embodiments, the level-2 SDN Controllers 235-245 can cooperatewith a cloud orchestrator in instantiating VNF elements for use in, forexample, the Core Network.

In one or more embodiments, a communication device 216 can operate incommunication with and/or as a part of a communications network 200. Thefunctionality of the communication device 216 may be provided by one ormore server computers, desktop computers, mobile telephones,smartphones, laptop computers, set-top boxes, other computing systems,and the like. In at least some embodiments the devices can includevirtually any IP enabled device, e.g., including without limitation homesecurity systems, vehicles, appliances, buildings, medical devices,wearable devices, smart meters, and the like. For examples, thecommunication devices can include any device operable according to anInternet of Things paradigm. It should be understood that thefunctionality of the communication device 216 can be provided by asingle device, by two similar devices, and/or by two or more dissimilardevices. For purposes of describing the concepts and technologiesdisclosed herein, the communication device 216 is described herein as aworkstation or personal computer. It should be understood that thisembodiment is illustrative, and should not be construed as beinglimiting in any way.

The communication device 216 can execute an operating system and one ormore application programs. The operating system can be a computerprogram that controls the operation of the communication device 216. Theapplication programs can be executable programs that are configured toexecute on top of the operating system to provide various functions.According to various embodiments, the application programs can includeweb browsers, productivity software, messaging applications,combinations thereof, or the like. In one or more embodiments, theapplication programs of the communication device 216 can includeapplications that enable interactions between the communication device216 and other devices or entities. In some contemplated embodiments, theapplication programs can provide functionality for interacting withand/or communicating with the communication network 200 and, in turn,having communications analyzed by the manager SDN controller 230 or,alternatively, any of the SDN Controllers 230-245 in the SDN network250.

According to various embodiments, the SDN network 250 can include and/oraccess resources, such as a service orchestrator, a software definednetwork controller, a cloud orchestrator, and/or other elements. Itshould be understood that the manager SDN controller 230, and any of theabove-described components, or combinations thereof, may be embodied asor in stand-alone devices or components thereof operating as part of orin communication with the communication network 200. As such, theillustrated embodiment should be understood as being illustrative ofonly some contemplated embodiments and should not be construed as beinglimiting in any way.

In one or more embodiments, the SDN network 250 can automaticallyevaluate application service requirements that have been requested fromthe communication system 200. In one embodiment, a service request canbe received from a subscriber, or customer, or customer device. Forexample, a request can be receive via a portal. The service request canbe provided to the soft manager SDN controller 230 for service creation,instantiation, and management. According to various embodiments, theservice request can be analyzed by the manager SDN controller 230. Inone embodiment, the manager SDN controller 230 can access or query theservice layer 225 to determine service requirements needed forfulfilling the service request.

In one or more embodiments, a service request can be received byequipment of a subscriber or customer (e.g., via the portal), andprovided to the SDN network 250 for service creation, instantiation, andmanagement. The service request can include application objects and/orrequests for particular services or functions. Thus, the service requestcan include objects that define service functions that are desired,requests for generation of services and/or requests for particularfunctionality, queries, combinations thereof, or the like. It should beunderstood that these examples are illustrative and therefore should notbe construed as being limiting in any way. According to variousembodiments, the service request can be analyzed by the SDN controller230-245 and a set composed of a directed graph and the associated modelor model files are selected. The model can define features of theservice and can generate in a programming language or format such asXML, Yang models, other types of files, combinations thereof, or thelike. The selected directed graph can be used at runtime to fill in theevent-specific details from the API, the resource allocations per thedirected graph and the resource model, and one or more state changes inthe network through the adapters.

In one or more embodiments, the communication device 216 can communicatewith the communication network 200 via a wireless communication link.For example, the communication device 216 can be a mobile communicationdevice 216 that communications via a cellular communication link througha Radio Access Network (RAN) technology. A mobility network 217, such asa 3GPP wireless network, e.g., an LTE network or a 5G network, canestablish wireless communications with the communication device 216,where the communication device 216 can move from cell to cell, whilemaintaining a communication session. In another example, thecommunication device 216 can communication with the communicationnetwork via a non-3GPP wireless link, e.g., a WiFi network link. TheWiFi network can be, for example, a local area network (LAN) that issupported by a router capable of wireless communications or can be anindividual device, such another mobile communication device 216 capableof acting as an intermediary (e.g., a Hot Spot). In one or moreembodiments, the communication network 200 can be a converged networkcapable of supporting a wide range of access, core and transportnetworks, such as wireline, wireless, satellite, 3GPP, non-3GPP, and/or5G. It is understood that the radio frequency spectrum used in wirelessaccess can include licensed spectrum, unlicensed spectrum andcombinations thereof.

In one or more embodiments, a Management Gateway (MGW) 242 can beincluded in the communication network 200. The MGW 242 can capturetraffic entering the communication network 200 from variouscommunication devices 216 and/or various Access Networks (AN) 217. TheMGW 242 can communicate with the SDN network 250, e.g., with the managerSDN controller 230, regarding traffic entering the communication network200. In one embodiment, the MGW 242 and the manager SDN controller 230can communicate via a communications protocol, such as an OpenFlow®protocol that provide access to a forwarding plane of a network device,such as a switch or router, over a network. OpenFlow® is a registeredtrademark of the Open Networking Foundation of Palo Alto, Calif. The MGW242 can inform the management SDN controller 230 of informationregarding services sought by one or more communication devices 230. Themanagement SDN controller 230 can analyze these services to determineservice functions and/or network data flows that would be required tofacilitate delivery of these services to the communication devices 216.

In one or more embodiments, the manager SDN controller 230 can query theservice layer 225 to determine the functional and/or resourcerequirements to provide the service to the communication device 216. Inone or more embodiments, the service requirements can include servicefeature data. In one or more embodiments, this service feature data canbe generated by or provided to the service layer 225 and/or the managerSDN controller 230 via interactions between the communication device 216and the portal. For example, in the process of making the servicerequest, the communication device 216 can make a series of selectionsfrom menus, drop-down lists, fields, tables, or other data or objectselection mechanisms that may be provided by the portal and/or theapplication programs executing on the communication device 216. In someembodiments, the application programs can include a web browserapplication and/or other application that can obtain data from theportal. In one or more embodiments, the application programs can use thedata to generate and present a user interface at the communicationdevice 216. The user interface can include possible service features,and a user or other entity can select the desired features, drag anddrop desired features, and/or otherwise indicate desired features in aservice.

In some embodiments, the SDN controller 230 can query the service layer225 to determine an occurrence of an exceptional functional and/orresource requirement. Upon detection or discover of such exceptionalrequirements, the SDN controller 230 can facilitate access to and/orprovisioning of a super slice 260. According to the subject disclosure,one or more super slices 260 can provide or otherwise supportprovisioning of the exceptional functional and/or resource requirements.

In one or more embodiments, the manager SDN controller 230 can analyzepolicies or policy defined for a service. This policy can includenetwork engineering rules, which can be defined by a network designer,engineer, business unit, operations personnel, or the like, or asubscriber policy, which can be defined during ordering of the service.Subscriber policies can include, for example, service level agreements(“SLAs”), location restrictions (e.g., locations at which the servicesare allowed or not allowed), bandwidth ranges, time restrictions (e.g.,times of day, days of week, or other times at which the service isallowed or not allowed), security restrictions or policies, combinationsthereof, or the like.

In one or more embodiments, the manager SDN controller 230 can determinefrom the service model one or more physical network functions or otherresources that will be needed or used to support the service. Themanager SDN controller 230 also can analyze the service model toidentify one or more virtual network functions or other functions thatwill support or provide the features of the service. The manager SDNcontroller 230 also can determine, via analysis of the service model,process flows between the various resources and/or functions used tosupport or provide the service features.

In one embodiment, the manager SDN controller 230 can communicate witheach of the instantiated SDN controllers 235-245 via a communicationinterface, such as an interface that applies OpenFlow® data networkprotocols. In addition, the SDN controllers 235, 240, 245 of level-2 tocan communicate among themselves to determine resource capabilities,capacities, shortages, failures, and/or warnings. In one or moreembodiments, if the manager SDN controller 230 determines that therequested service can be performed, within system margins, using thecurrently instantiated SDN controllers 235, 240, 245, then the managerSDN controller 230 can decide to direct the SDN controllers 235, 240,245 to perform the service for the communication device 216.Alternatively, if the manager SDN controller 230 determines a shortageor shortfall in a needed resource, then the manager SDN controller 230can direct instantiation of one or more new SDN controller 235-245 toperform all or part of the requested service. For example, the managerSDN controller 230 may determine that the service request associatedwith the example communication device 216, or many communication devices216, or merely received at the communication network 210 from anindeterminate device (e.g., a request for resources from anothernetwork) requires additional core SDN controller capacity 240. In thiscase, the manager SDN controller 230 can direct the instantiation ofadditional core SDN controller 240 capacity from a set of configurableSDN controller devices at the cloud.

In one or more embodiments, the access SDN controller 235 can control,direct, configure, and monitor access resources 217 and 219 for thenetwork 200, such as eNodeB controllers, RAN controllers, and or WiFicontrollers. In another example, the core SDN controller 240 cancontrol, direct, configure, and monitor core resources 274A-276C for thecore network of the communication network 200, such as Gateways (GW) forControl Plane (CP) 274A-C, User Plane (UP) 276A-C, and/or legacy (i.e.,combined user and control plane). In another example, the transport SDNcontroller can control, direct, configure, and monitor transport layerservices 254, such as a Multiprotocol Label Switching (MPLS) network,Fiber Optics network, and/or a Backbone network.

In one or more embodiments, the manager SDN controller 230, adapted tosupport level-3 functionality, can manage one or more sets of level-2SDN controllers 235-245 in the SDN network 250. The manager SDNcontroller 230 can configure and/or reconfigure the instantiated SDNcontrollers 235-245 to optimize the SDN network 250 according to loadingcreated by the service requests. For example, the manager SDN controller230 can automatically instantiate multiple levels of fully distributedSDN controllers 235-245. Likewise the level-2 SDN controllers 235-245can instantiate and/or configure and/or reconfigure VNF elements274A-276C at level-1. Each of the SDN controllers 230-245 can supportinstantiation “on the fly” based on new requests, the ending of oldrequests, monitoring network traffic, and/or requesting loadinginformation from any of the other SDN controllers 235-245 and/or the VNFelements 274A-276C.

Alternatively or in addition, one or more of the SDN controllers 230,235, 240, 245 can support instantiation “on the fly” based on adetermination that a particular slice is unable and/or unlikely adaptedto fulfill or otherwise satisfy one or more services, e.g., based onexceptional functional and/or resource requirements. It is understoodthat one or more of the SDN controllers 230-245 alone or in combinationwith other network and/or service assets, can determine an occurrence ofan exceptional functional and/or resource requirements. In someembodiments, determination of the exceptional requirements can be basedon a network status, a service requirement and/or a user equipmentrequirement. Alternatively or in addition, the exceptional requirementcan be based at least in part on another entity, such as a third partyentity. The third party entity can include, without limitation, anoperation and maintenance service provider, an equipment and/or softwarevendor requirement—this can include networking equipment including anyof the network devices disclosed herein, underlying hardware and/orsoftware supporting the VNFs, end user equipment and the like. Stillother third party entities can include, without limitation, serviceproviders, governmental agencies, and so on.

For example, the manager SDN controller 230 can instantiated and/ordecommission and/or reconfigure VNF elements 274A-276C. For example, ina streaming media application, such as a Netflix™ Video Deliveryapplication, the manager SDN controller 230 can determine that networkdemands for the access SDN controller 235 and transport SDN controller245 may be relatively large for a given set of communication devices216, while the core SDN controller 240 demands for these communicationdevices 216 may be relatively normal. The manager SDN controller 230 canlook at the available resources and capacities for the currentlyinstantiated SDN controllers 235, 240, 245 that are support thesecommunication devices 216. If the demands of the media streamingapplication exceed the available resources, then the manager SDNcontroller 230 can automatically address the issue by, for example,instantiating additional access SDN controller 235 and transport SDNcontroller 245 resources. However, if it is determined that exceedingthe available resources is based on an exceptional condition, e.g., onethat goes beyond the scope of routinely provisioned services of thedefault and/or dedicated slices 110, 112 (FIG. 1), requests can beinitiated to instantiate, allocate or otherwise provide access to thesuper slice 260.

In at least some embodiments, more than one super slice 260 may exist.For example, super slices can be provisioned according to one or more ofservice application, scope, capacity, location, network conditions,business rules, policies, and the like. Accordingly, one or more of thecontrollers 230-245 and/or an SSF 134 and/or NSSF 128 can identifyand/or otherwise initiate a provisioning of an appropriate super slice160. This can include selecting a particular super slice 160 of apredetermined group of super slices 160. Although super slices 160 maybe predetermined, they are not necessarily instantiated until an actualand/or perceived time of need. Alternatively or in addition, a superslice 160 can be identified or otherwise configured responsive to anactual and/or perceived time of need. In such scenarios, it isenvisioned that a number and/or type of NVFs can be determined at theactual and/or perceived time of need. The particular super slice 260 canthen be instantiated and/or identified for future instantiation based onthe identification and/or configuration.

In one or more embodiments, the manager SDN controller 230 may determinethat sufficient resources exist at the currently instantiated access SDNcontroller 235 and transport SDN controller 245 resources, however, thepriorities of these resources need to be adjusted. For example, where aheavy streaming media loading is identified, the access SDN controller235 and transport SDN controller 245 resources may be given higherpriority in comparison to the core SDN controller 240. Conversely, if aheavy loading of Voice over IP (VoIP) services is identified, then themanager SDN controller 230 can automatically place the core network SDNcontroller 240 into higher priority in comparison to access network SDNcontroller 235 and transport network SDN controller 245.

In one or more embodiments, a SDN-controlled network, using networkfunction virtualization, software defined networking, and/or cloud-basedconcepts, can provide flexibility in number, type and/or configurationof virtual networks, sometimes referred to as flexible network slicing.Network slicing facilitates distributed functionality, e.g., to supportdiverged types of services and requirements, such as those supportingfuture developments in wireless networks including 5G networks. SDNcontrollers 230 can provide control and configuration to supportdifferent network slices on appropriate network slices or clouds 262A-Cby instantiating and controlling a proper sets of VNF elements 274A-276Cand by the optimal distribution of these VNF elements 274A-276C based onapplication and service requirements.

Generally speaking, network slicing is a network management technique inwhich compute and/or connectivity resources in a communications networkare divided to create a set of different virtual networks. For example,network slices can be supported by virtual network functionsinstantiated upon generic computing resources to provide specificnetwork functions. Without limitation, network slices can be used in oneor more of a core network, a radio access network, a backhaul network.Isolation provided by the network slices can be applied to differentoperators, different types of services, different types of networktraffic, different users and/or classes of users, and the like.

In one or more embodiments, network slicing can be used by the SDNnetwork to support multiple virtual networks behind the air interface(s)217 of the communication network. The slicing of the network intomultiple virtual networks can provide optimal support for differentRadio Access Networks (RAN) and/or different service types runningacross a single RAN. Further, in one or more embodiments, flexibledistribution of the access, edge, and core elements of the network cloudcan provide optimal support regarding latency and/or service isolationfor different apps and service requirements. Connectivity betweencomputing resources can be allocated so that traffic of one slice can beisolated from that of another. Isolation can be based on one or more ofnetwork operator, service, application, user, user equipment, level ofsubscription service, and so on. By way of example, one slice can beconfigured to suit the needs of a Machine Type Communication (MTC)service, which typically generate large numbers of short transmissionsthat do not require ultra-reliable connections. Another slice cansupport Mobile Broadband (MBB), or enhanced Mobile Broadband (eMBB)services, having different requirements. Network slices created to servethe needs of different services may be built upon the resourcesallocated to a network operator within a slice that isolates the networkoperator from other network operators on a set of resources associatedwith a service provider.

In one or more embodiments, the SDN Network 250 can determine whatservice(s) is being used and which external network and/or networkoperator, e.g., by way of an Access Point Node (APN), is being used forthe specific traffic. In one embodiment, the analysis can be performedby a SDN controller 230-245, which derive information either directlyfrom communications entering the network 200 form one or morecommunication devices 216 or from a MGW 242 that is monitoring this typeof traffic. In one or more embodiments, a SDN Controller 230 can performanalysis that determine a detailed granularity of the specific servicesbeing sought by or provided to the communication device 216. Thisdetailed granularity can reveal sets of service functions (e.g.,identifying servers, providing connections to applications, verifyingauthenticity, providing control plane and user plane functions) that arenecessary for facilitating the delivery of services. The detailedgranularity can also include determining various data pathways, withinthe network 200 and beyond, necessary for facilitating the delivery ofservices. The SDN Controller 230 can instantiate VNF elements 274A, 276Athat can cause traffic to be sent to respective destinations such as 4G,4G+, or 5G APNs, based upon breaking up the specific services requestedinto the types of service functions, resources, data accesses, and/ornetwork data paths. The VNF elements that are composed, configured, andchained by the SDN Controller 230 for implementing the necessary servicefunctions are, in turn, instantiated into the 5G network 200 in networklocations that optimize one or more characteristics of the servicefunctions and/or network data paths.

Examples of flexible, adaptive networks, such as the illustrativeexample communication network 200, are disclosed in commonly owned, U.S.patent application Ser. No. 15/344,692, entitled “Method and Apparatusfor a Responsive Software Defined Network,” filed on Nov. 7, 2016, andincorporated herein by reference in its entirety. Additionally,techniques related to dynamic network routing in a software definednetwork are disclosed in U.S. patent application Ser. No. 15/351,618,entitled “Method and Apparatus for Dynamic Network Routing in a SoftwareDefined Network,” filed on Nov. 15, 2016, and also incorporated hereinby reference in its entirety.

FIG. 3A depicts illustrative embodiments of a process 300 for managingnetwork resources used in portions of the system described in FIGS. 1and 2. A determination is made at step 302 as to whether a request hasbeen made to access a special network slice. In at least someembodiments, one or more default and/or dedicated slices are employed byequipment of a user at any given time. For example, a user may bestreaming video to a smart phone, while engaging in an instant messagingdiscussion with a coworker, or browsing the Web. Accordingly,appropriate dedicated network slices, e.g., for streaming media, instantmessage, browsing and so on are initiated and used by associatedfunctions to deliver the different services to the user device. In thisscenario, one or more of the utilized network slice(s) are identified.Identification can be obtained from one or more of the mGW, an SDNcontroller, a NSSF, and the like.

A determination is made at step 304 as to whether an exceptionalrequirement exists. Exceptional requirements and/or conditions generallyrelate to circumstances during which any allocated network slices, e.g.,those determined in step 302, are unable to reliably provide thecorresponding services and/or functions. Exceptional requirements can bedetected in any suitable manner. For example, resource requests from aparticular premium function, service and/or service provider.Alternatively or in addition, the exceptional requirement can bedetermined according a location of equipment of the user, e.g., in acountry or region that requires heightened security measures. Likewise,the exceptional requirement can be determined by a report and/or messagefrom the network service provider, subscribed service provider,operation and maintenance provider, and/or a third party, such as anenterprise administrator, a network operator, a security monitor, agovernment agency, and the like.

To the extent that it is determined that an exceptional requirementexists, a request is made at step 306 to access a special network slice.Access to the special network slice can include a request to access apredetermined slice. The request can include an identity of the slice,e.g., as it may be associated with predetermined special slicerequirements. In at least some instances, the request identifies arequest for access to a special slice without necessarily identifyingany particular special slice. For example, the request can include anidentification of one or more of a service, a function, and/or afunctional requirement associated with the identification of one or moreof the first network slice at step 203 and/or the exceptionalrequirement at step 304.

In at least some embodiments, an association of one or more specialslices and/or special slice requirements is maintained. This can bemaintained by one or more of a network service provider, subscribedservice provider, operation and maintenance provider, and/or a thirdparty, such as an enterprise administrator, a network operator, asecurity monitor, a government agency, and the like. The association canbe based on one or more of a predictive analysis of special slicerequirements, e.g., NVFs to be accommodated by the special slice.Alternatively or in addition, the association can be based on one ormore of a level of subscription, a user identity, an equipment type, aservice type, a condition of the network, and the like.

To the extent that an exceptional requirement does not exist, theprocess continues from step 304, e.g., continuing to monitor for anoccurrence of an exceptional requirement. For example, separatemonitoring can occur for each identified network slice. Consider asituation in which user equipment 104 is accessing services by way ofmultiple dedicated slices 112 (FIG. 1). Each utilized slice can beidentified, e.g., at step 302, and for each identified slices, the atleast a portion of the process 300 can be repeated.

In response to the request to access the special network slice, adetermination is made at step 308 as to whether the request isauthorized and/or the special network is available. It is understoodthat in at least some instances, the process can include an additionalstep of identifying and/or otherwise defining and/or describing thespecial network slice. In some embodiments, it is envisioned that one ormore special slices can be predetermined, e.g., based upon adetermination of exceptional requirements beforehand. Based on theexceptional requirements, alone or in combination with a determinationof dedicated slices, e.g., typical dedicated slices, the special networkslices can be identified and/or otherwise described.

Authorization to access the special slice can be determined beforehand,e.g., at a time of subscription whereby a subscriber contracts foravailability of special slices. In these instances, the authorizationcan be included in a service contract, e.g., a service level agreement.It is further understood that such authorization, whether contracted foror otherwise, may depend on one or more of an identity of the user, anidentity and/or type of the user equipment, a type of service, asubscription level, and/or a priority of one or more of the user, theservice, the function. In at least some embodiments, authorization canbe subject to one or more of policies, business rules, networkconditions, e.g., capacity, usage, and the like, alone or in combinationwith any of the foregoing.

To the extent that it is determined at step 308 that authorization isnot obtained and/or the special network slice is not available, a reportto that affect can be optionally prepared and/or requested at 318 (shownin phantom). In at least some embodiments, alternative measures and/orsuggestions can be identified and/or otherwise provided optionally at320 (also shown in phantom). Alternative measures can include, withoutlimitation, a recommendation to try a different network, e.g., to move auser from a macro cell to a WiFi hotspot, providing access toalternative services in place of the special network slice. In someembodiments, the alternative measure may recommend and/or inform arequesting entity that the request should be re-submitted and/or queuedfor processing at a later time. Still further, it is envisioned thatalternative measures can include an offer to modify an SLA, e.g., toprovide enhanced and/or increased access to special network slice(s).

Alternatively or in addition, one or more of the special slices areidentified responsive to the identification of one or more of the firstnetwork slice at step 302 and/or identification of the exceptionalrequirement at step 304. In at least some instances, parameters of theexceptional requirement, e.g., processing capacity, networking capacity,communication capacity, and the like are identified and usable.

To the extent it is determined at step 308, that the special networkslice is available and access is authorized, access to the specialnetwork slice is initiated at 310. In some embodiments, access to thespecial network slice is provided in place of a dedicated network sliceassociated with the exceptional requirement. Alternatively or inaddition, access to the special network slice is provided in combinationwith the dedicated network slice associated with the exceptionalrequirement. For example, the special slice can be linked, joined orotherwise chained with the dedicated slice and/or a default slice. Onceaccess has been established, the special slice is accessed at step 312.

It is envisioned that in at least some embodiments, access to specialslices should not be granted and/or authorized for duration longer thannecessary to accommodate the exceptional requirement determined at 304.In this manner, excess network resource capacity provided by way of thespecial slice(s) is released when it is determined that it is no longerneeded. Such release frees up network resources, e.g., by way of thespecial slice and/or underlying hardware and SDN resources associatedwith the special slice. Accordingly, it can be determined, e.g., at step314, whether the exceptional requirement remains. In some embodiments, acontinued status of the exceptional requirement can be determined in amanner similar to that used in association with step 304. Alternativelyor in addition, other means can be used, e.g., by evaluating a systemperformance measure, e.g., a processing utilization, a memoryutilization, a communication utilization, and so on. Such utilizationscan be determined based on the special network slice, whereby resolutionof the exceptional requirement is observable.

Alternatively or in addition, a determination as to persistence of theexceptional requirement at 314 can be determined according to one ormore of a timer, a buffer depth, a message, e.g., a message and/orstatus reported by or in association with a service, a function and/or acommunication device associated with the authorized access to thespecial slice.

To the extent that it determined that the exceptional requirementpersists at step 314, the process continues to step 312, utilizing thespecial network slice as described above. To the extent that isdetermined that the exceptional requirement no longer persists at 314,the process continues to step 316, at which access to the specialnetwork slice can be terminated. Termination can include any efficientmanner, e.g., by initiating a request to one or more of the mGW, the SDNcontroller and/or orchestrator, to terminate access. In at least someembodiments, termination of access to the network slice is accompaniedby resolution of utilization of the original first network slice, e.g.,at step 302 and/or an equivalent slice.

FIG. 3B depicts another illustrative embodiments of a process 350 formanaging network resources used in portions of the system described inFIGS. 1 and 2. The process 350 includes determining a request to accessa special network slice at 352. A determination is made at step 354 asto whether the requested special network slice is available and/orauthorized. In at least some embodiments, failure of availability and/orauthorization to the special network slices at step 354 can be reportedat step 318 (shown in phantom). To the extent that the requested specialnetwork slice is available and/or authorized, access to the specialnetwork slice is facilitated at 356. The process 350 monitors whetherthe exceptional requirement persists at 358. To the extent it no longerexists, the process terminates access to the special network slice at360.

While for purposes of simplicity of explanation, the respectiveprocesses are shown and described as a series of blocks in FIG. 3, it isto be understood and appreciated that the claimed subject matter is notlimited by the order of the blocks, as some blocks may occur indifferent orders and/or concurrently with other blocks from what isdepicted and described herein. Moreover, not all illustrated blocks maybe required to implement the methods described herein.

FIG. 4 depicts an illustrative embodiment of a communication system 400for providing various communication services, such as delivering mediacontent. The communication system 400 can represent an interactive medianetwork, such as an interactive television system (e.g., an InternetProtocol Television (IPTV) media system). Communication system 400 canbe overlaid or operably coupled with one or more of the communicationsystems 100, 200 of FIGS. 1 and/or 2, as another representativeembodiment of communication system 400. For instance, one or moredevices illustrated in the communication system 400 of FIG. 4, canfacilitate determination of a first group of virtual network functionsinstantiated within a software defined network, e.g., default slices 112(FIG. 1) and adapted to perform a first activity that facilitatesdelivery of a dedicated service to wireless equipment of a first userunder normal conditions. One or more of the devices of the communicationsystem 400 can determine an occurrence of an exceptional condition,whereby delivery of the dedicated service to the wireless equipmentrequires a second activity that first group of virtual network functionsis not designated to perform the second activity. In at least someembodiments, the first group of virtual network functions is incapableof performing the second activity. Access to a second group of virtualnetwork functions is facilitated, responsive to the determining of theoccurrence of the condition. The second group of virtual networkfunctions when instantiated within the software defined network areadapted to perform the second activity that facilitates delivery of thededicated service to the wireless equipment of the first user during theoccurrence of the condition.

In one or more embodiments, the communication system 400 can include asuper head-end office (SHO) 410 with at least one super headend officeserver (SHS) 411 which receives media content from satellite and/orterrestrial communication systems. In the present context, media contentcan represent, for example, audio content, moving image content such as2D or 3D videos, video games, virtual reality content, still imagecontent, and combinations thereof. The SHS server 411 can forwardpackets associated with the media content to one or more video head-endservers (VHS) 414 via a network of video head-end offices (VHO) 412according to a multicast communication protocol. The VHS 414 candistribute multimedia broadcast content via an access network 418 tocommercial and/or residential buildings 402 housing a gateway 404 (suchas a residential or commercial gateway).

The access network 418 can represent a group of digital subscriber lineaccess multiplexers (DSLAMs) located in a central office or a servicearea interface that provide broadband services over fiber optical linksor copper twisted pairs 419 to buildings 402. The gateway 404 can usecommunication technology to distribute broadcast signals to mediaprocessors 406 such as Set-Top Boxes (STBs) which in turn presentbroadcast channels to media devices 408 such as computers or televisionsets managed in some instances by a media controller 407 (such as aninfrared or RF remote controller).

The gateway 404, the media processors 406, and media devices 408 canutilize tethered communication technologies (such as coaxial, powerlineor phone line wiring) or can operate over a wireless access protocolsuch as Wireless Fidelity (WiFi), Bluetooth®, Zigbee®, or other presentor next generation local or personal area wireless network technologies.By way of these interfaces, unicast communications can also be invokedbetween the media processors 406 and subsystems of the IPTV media systemfor services such as video-on-demand (VoD), browsing an electronicprogramming guide (EPG), or other infrastructure services.

A satellite broadcast television system 429 can be used in the mediasystem of FIG. 4. The satellite broadcast television system can beoverlaid, operably coupled with, or replace the IPTV system as anotherrepresentative embodiment of communication system 400. In thisembodiment, signals transmitted by a satellite 415 that include mediacontent can be received by a satellite dish receiver 431 coupled to thebuilding 402. Modulated signals received by the satellite dish receiver431 can be transferred to the media processors 406 for demodulating,decoding, encoding, and/or distributing broadcast channels to the mediadevices 408. The media processors 406 can be equipped with a broadbandport to an Internet Service Provider (ISP) network 432 to enableinteractive services such as VoD and EPG as described above.

In yet another embodiment, an analog or digital cable broadcastdistribution system such as cable TV system 433 can be overlaid,operably coupled with, or replace the IPTV system and/or the satelliteTV system as another representative embodiment of communication system400. In this embodiment, the cable TV system 433 can also provideInternet, telephony, and interactive media services. System 400 enablesvarious types of interactive television and/or services including IPTV,cable and/or satellite.

The subject disclosure can apply to other present or next generationover-the-air and/or landline media content services system.

Some of the network elements of the IPTV media system can be coupled toone or more computing devices 430, a portion of which can operate as aweb server for providing web portal services over the ISP network 432 towireline media devices 408 or wireless communication devices 416.

The communication system 400 can also provide for all or a portion ofthe computing devices 430 to function as a network slice selectionfunction (herein referred to as NSSF 430). The NSSF 430 can usecomputing and communication technology to perform function 462, whichcan include among other things, the slice selection techniques describedby processes 300, 350 of FIGS. 3A-3B. For instance, function 462 ofserver 430 can be similar to the functions described for the NSSF 128 ofFIG. 1 in accordance with the processes 300, 350 of FIGS. 3A-3B. Themobile network core 480 and/or the cell site 417 can be provisioned withsoftware functions 464 and 466, respectively, to utilize the services ofthe NSSF 430. For instance, functions 464 and 466 can be similar to thefunctions described for NSSF 128 of FIG. 1 in accordance with theprocesses 300, 350 of FIGS. 3A-3B.

Multiple forms of media services can be offered to media devices overlandline technologies such as those described above. Additionally, mediaservices can be offered to media devices by way of a wireless accessbase station 417 operating according to common wireless access protocolssuch as Global System for Mobile or GSM, Code Division Multiple Accessor CDMA, Time Division Multiple Access or TDMA, Universal MobileTelecommunications or UMTS, World interoperability for Microwave orWiMAX, Software Defined Radio or SDR, Long Term Evolution or LTE, and soon. Other present and next generation wide area wireless access networktechnologies can be used in one or more embodiments of the subjectdisclosure.

FIG. 5 depicts an illustrative embodiment of a communication system 500employing an IP Multimedia Subsystem (IMS) network architecture tofacilitate the combined services of circuit-switched and packet-switchedsystems. Communication system 500 can be overlaid or operably coupledwith communication systems 100, 200 of FIGS. 1 and/or 2 andcommunication system 400 as another representative embodiment ofcommunication system 400. One or more of the devices of thecommunication system 500 can facilitate determination of a first groupof virtual network functions instantiated within a software definednetwork, e.g., default slices 112 (FIG. 1) and adapted to perform afirst activity that facilitates delivery of a dedicated service towireless equipment of a first user under normal conditions. One or moreof the devices of the communication system 400 can determine anoccurrence of an exceptional condition, whereby delivery of thededicated service to the wireless equipment requires a second activitythat first group of virtual network functions is not designated toperform the second activity. Access to a second group of virtual networkfunctions is facilitated, responsive to the determining of theoccurrence of the condition. The second group of virtual networkfunctions when instantiated within the software defined network areadapted to perform the second activity that facilitates delivery of thededicated service to the wireless equipment of the first user during theoccurrence of the condition.

Communication system 500 can comprise a Home Subscriber Server (HSS)540, a tElephone NUmber Mapping (ENUM) server 530, and other networkelements of an IMS network 550. The IMS network 550 can establishcommunications between IMS-compliant communication devices (CDs) 501,502, Public Switched Telephone Network (PSTN) CDs 503, 505, andcombinations thereof by way of a Media Gateway Control Function (MGCF)520 coupled to a PSTN network 560. The MGCF 520 need not be used when acommunication session involves IMS CD to IMS CD communications. Acommunication session involving at least one PSTN CD may utilize theMGCF 520.

IMS CDs 501, 502 can register with the IMS network 550 by contacting aProxy Call Session Control Function (P-CSCF) which communicates with aninterrogating CSCF (I-CSCF), which in turn, communicates with a ServingCSCF (S-CSCF) to register the CDs with the HSS 540. To initiate acommunication session between CDs, an originating IMS CD 501 can submita Session Initiation Protocol (SIP INVITE) message to an originatingP-CSCF 504 which communicates with a corresponding originating S-CSCF506. The originating S-CSCF 506 can submit the SIP INVITE message to oneor more application servers (ASs) 517 that can provide a variety ofservices to IMS subscribers.

For example, the application servers 517 can be used to performoriginating call feature treatment functions on the calling party numberreceived by the originating S-CSCF 506 in the SIP INVITE message.Originating treatment functions can include determining whether thecalling party number has international calling services, call IDblocking, calling name blocking, 7-digit dialing, and/or is requestingspecial telephony features (e.g., *72 forward calls, *73 cancel callforwarding, *67 for caller ID blocking, and so on). Based on initialfilter criteria (iFCs) in a subscriber profile associated with a CD, oneor more application servers may be invoked to provide various calloriginating feature services.

Additionally, the originating S-CSCF 506 can submit queries to the ENUMsystem 530 to translate an E.164 telephone number in the SIP INVITEmessage to a SIP Uniform Resource Identifier (URI) if the terminatingcommunication device is IMS-compliant. The SIP URI can be used by anInterrogating CSCF (I-CSCF) 507 to submit a query to the HSS 540 toidentify a terminating S-CSCF 514 associated with a terminating IMS CDsuch as reference 502. Once identified, the I-CSCF 507 can submit theSIP INVITE message to the terminating S-CSCF 514. The terminating S-CSCF514 can then identify a terminating P-CSCF 516 associated with theterminating CD 502. The P-CSCF 516 may then signal the CD 502 toestablish Voice over Internet Protocol (VoIP) communication services,thereby enabling the calling and called parties to engage in voiceand/or data communications. Based on the iFCs in the subscriber profile,one or more application servers may be invoked to provide various callterminating feature services, such as call forwarding, do not disturb,music tones, simultaneous ringing, sequential ringing, etc.

In some instances the aforementioned communication process issymmetrical. Accordingly, the terms “originating” and “terminating” inFIG. 5 may be interchangeable. It is further noted that communicationsystem 500 can be adapted to support video conferencing. In addition,communication system 500 can be adapted to provide the IMS CDs 501, 502with the multimedia and Internet services of communication system 400 ofFIG. 4.

If the terminating communication device is instead a PSTN CD such as CD503 or CD 505 (in instances where the cellular phone only supportscircuit-switched voice communications), the ENUM system 530 can respondwith an unsuccessful address resolution which can cause the originatingS-CSCF 506 to forward the call to the MGCF 520 via a Breakout GatewayControl Function (BGCF) 519. The MGCF 520 can then initiate the call tothe terminating PSTN CD over the PSTN network 560 to enable the callingand called parties to engage in voice and/or data communications.

It is further appreciated that the CDs of FIG. 5 can operate as wirelineor wireless devices. For example, the CDs of FIG. 5 can becommunicatively coupled to a cellular base station 521, a femtocell, aWiFi router, a Digital Enhanced Cordless Telecommunications (DECT) baseunit, or another suitable wireless access unit to establishcommunications with the IMS network 550 of FIG. 5. The cellular accessbase station 521 can operate according to common wireless accessprotocols such as GSM, CDMA, TDMA, UMTS, WiMax, SDR, LTE, and so on.Other present and next generation wireless network technologies can beused by one or more embodiments of the subject disclosure. Accordingly,multiple wireline and wireless communication technologies can be used bythe CDs of FIG. 5.

Cellular phones supporting LTE can support packet-switched voice andpacket-switched data communications and thus may operate asIMS-compliant mobile devices. In this embodiment, the cellular basestation 521 may communicate directly with the IMS network 550 as shownby the arrow connecting the cellular base station 521 and the P-CSCF516.

Alternative forms of a CSCF can operate in a device, system, component,or other form of centralized or distributed hardware and/or software.Indeed, a respective CSCF may be embodied as a respective CSCF systemhaving one or more computers or servers, either centralized ordistributed, where each computer or server may be configured to performor provide, in whole or in part, any method, step, or functionalitydescribed herein in accordance with a respective CSCF. Likewise, otherfunctions, servers and computers described herein, including but notlimited to, the HSS, the ENUM server, the BGCF, and the MGCF, can beembodied in a respective system having one or more computers or servers,either centralized or distributed, where each computer or server may beconfigured to perform or provide, in whole or in part, any method, step,or functionality described herein in accordance with a respectivefunction, server, or computer.

The NSSF 430 of FIG. 4 can be operably coupled to communication system500 for purposes similar to those described above. The NSSF 430 canperform function 462 and thereby provide super-slice access services tothe CDs 501, 502, 503 and 505 of FIG. 5 similar to the functionsdescribed for the NSSF 128 of FIG. 1 in accordance with processes 300,350 of FIGS. 3A-3B. The mobile network 521, which can be adapted withsoftware to perform function 572 to utilize the services of the NSSF430, similar to the functions described for mobile core network 480and/or cell site 417 of FIG. 4 in accordance with processes 300, 350 ofFIGS. 3A-3B. The NSSF 430 can be an integral part of the applicationserver(s) 517 performing function 574, which can be substantiallysimilar to function 462 and adapted to the operations of the IMS network550.

For illustration purposes only, the terms S-CSCF, P-CSCF, I-CSCF, and soon, can be server devices, but may be referred to in the subjectdisclosure without the word “server.” It is also understood that anyform of a CSCF server can operate in a device, system, component, orother form of centralized or distributed hardware and software. It isfurther noted that these terms and other terms such as DIAMETER commandsare terms can include features, methodologies, and/or fields that may bedescribed in whole or in part by standards bodies such as 3^(rd)Generation Partnership Project (3GPP). It is further noted that some orall embodiments of the subject disclosure may in whole or in partmodify, supplement, or otherwise supersede final or proposed standardspublished and promulgated by 3GPP.

FIG. 6 depicts an illustrative embodiment of a web portal 602 of acommunication system 600. Communication system 600 can be overlaid oroperably coupled with communication systems 100, 200 of FIGS. 1 and/or2, communication system 400, and/or communication system 500 as anotherrepresentative embodiment of communication systems 100, 200 of FIGS. 1and/or 2, communication system 400, and/or communication system 500. Theweb portal 602 can be used for managing services of the communicationsystems 100, 200 of FIGS. 1 and/or 2 and communication systems 400-500.A web page of the web portal 602 can be accessed by a Uniform ResourceLocator (URL) with an Internet browser using an Internet-capablecommunication device such as those described in FIGS. 1 and/or 2 andFIGS. 4-5. The web portal 602 can be configured, for example, to accessa media processor 406 and services managed thereby such as a DigitalVideo Recorder (DVR), a Video on Demand (VoD) catalog, an ElectronicProgramming Guide (EPG), or a personal catalog (such as personal videos,pictures, audio recordings, etc.) stored at the media processor 406. Theweb portal 602 can also be used for provisioning IMS services describedearlier, provisioning Internet services, provisioning cellular phoneservices, and so on.

The web portal 602 can further be utilized to manage and provisionsoftware applications 462-466, and 572-574 to adapt these applicationsas may be desired by subscribers and/or service providers ofcommunication systems 100, 200 of FIGS. 1 and/or 2, and communicationsystems 400-500. For instance, users of the services provided by thedefault slice 110, the premium service 106, and/or the NSSF 128 can loginto their on-line accounts and provision the servers 110 or server 430with subscription levers, equipment types, business rules, policies,authorization and/or access parameters and/or requirements, and so on.Network operators, service providers, and/or other third parties, canlog onto an administrator account to provision, monitor and/or maintainat least respective portions of the communication systems 100, 200 ofFIGS. 1 and/or 2 and/or the NSSF 430.

FIG. 7 depicts an illustrative embodiment of a communication device 700.Communication device 700 can serve in whole or in part as anillustrative embodiment of the devices depicted in FIGS. 1 and/or 2, andFIGS. 4-5 and can be configured to perform portions of the processes300, 350 of FIGS. 3A-3B.

Communication device 700 can comprise a wireline and/or wirelesstransceiver 702 (herein transceiver 702), a user interface (UI) 704, apower supply 714, a location receiver 716, a motion sensor 718, anorientation sensor 720, and a controller 706 for managing operationsthereof. The transceiver 702 can support short-range or long-rangewireless access technologies such as Bluetooth®, ZigBee®, WiFi, DECT, orcellular communication technologies, just to mention a few (Bluetooth®and ZigBee® are trademarks registered by the Bluetooth® Special InterestGroup and the ZigBee® Alliance, respectively). Cellular technologies caninclude, for example, CDMA-1×, UMTS/HSDPA, GSM/GPRS, TDMA/EDGE, EV/DO,WiMAX, SDR, LTE, as well as other next generation wireless communicationtechnologies as they arise. The transceiver 702 can also be adapted tosupport circuit-switched wireline access technologies (such as PSTN),packet-switched wireline access technologies (such as TCP/IP, VoIP,etc.), and combinations thereof.

The UI 704 can include a depressible or touch-sensitive keypad 708 witha navigation mechanism such as a roller ball, a joystick, a mouse, or anavigation disk for manipulating operations of the communication device700. The keypad 708 can be an integral part of a housing assembly of thecommunication device 700 or an independent device operably coupledthereto by a tethered wireline interface (such as a USB cable) or awireless interface supporting for example Bluetooth®. The keypad 708 canrepresent a numeric keypad commonly used by phones, and/or a QWERTYkeypad with alphanumeric keys. The UI 704 can further include a display710 such as monochrome or color LCD (Liquid Crystal Display), OLED(Organic Light Emitting Diode) or other suitable display technology forconveying images to an end user of the communication device 700. In anembodiment where the display 710 is touch-sensitive, a portion or all ofthe keypad 708 can be presented by way of the display 710 withnavigation features.

The display 710 can use touch screen technology to also serve as a userinterface for detecting user input. As a touch screen display, thecommunication device 700 can be adapted to present a user interface withgraphical user interface (GUI) elements that can be selected by a userwith a touch of a finger. The touch screen display 710 can be equippedwith capacitive, resistive or other forms of sensing technology todetect how much surface area of a user's finger has been placed on aportion of the touch screen display. This sensing information can beused to control the manipulation of the GUI elements or other functionsof the user interface. The display 710 can be an integral part of thehousing assembly of the communication device 700 or an independentdevice communicatively coupled thereto by a tethered wireline interface(such as a cable) or a wireless interface.

The UI 704 can also include an audio system 712 that utilizes audiotechnology for conveying low volume audio (such as audio heard inproximity of a human ear) and high volume audio (such as speakerphonefor hands free operation). The audio system 712 can further include amicrophone for receiving audible signals of an end user. The audiosystem 712 can also be used for voice recognition applications. The UI704 can further include an image sensor 713 such as a charged coupleddevice (CCD) camera for capturing still or moving images.

The power supply 714 can utilize common power management technologiessuch as replaceable and rechargeable batteries, supply regulationtechnologies, and/or charging system technologies for supplying energyto the components of the communication device 700 to facilitatelong-range or short-range portable applications. Alternatively, or incombination, the charging system can utilize external power sources suchas DC power supplied over a physical interface such as a USB port orother suitable tethering technologies.

The location receiver 716 can utilize location technology such as aglobal positioning system (GPS) receiver capable of assisted GPS foridentifying a location of the communication device 700 based on signalsgenerated by a constellation of GPS satellites, which can be used forfacilitating location services such as navigation. The motion sensor 718can utilize motion sensing technology such as an accelerometer, agyroscope, or other suitable motion sensing technology to detect motionof the communication device 700 in three-dimensional space. Theorientation sensor 720 can utilize orientation sensing technology suchas a magnetometer to detect the orientation of the communication device700 (north, south, west, and east, as well as combined orientations indegrees, minutes, or other suitable orientation metrics).

The communication device 700 can use the transceiver 702 to alsodetermine a proximity to a cellular, WiFi, Bluetooth®, or other wirelessaccess points by sensing techniques such as utilizing a received signalstrength indicator (RSSI) and/or signal time of arrival (TOA) or time offlight (TOF) measurements. The controller 706 can utilize computingtechnologies such as a microprocessor, a digital signal processor (DSP),programmable gate arrays, application specific integrated circuits,and/or a video processor with associated storage memory such as Flash,ROM, RAM, SRAM, DRAM or other storage technologies for executingcomputer instructions, controlling, and processing data supplied by theaforementioned components of the communication device 700.

Other components not shown in FIG. 7 can be used in one or moreembodiments of the subject disclosure. For instance, the communicationdevice 700 can include a reset button (not shown). The reset button canbe used to reset the controller 706 of the communication device 700. Inyet another embodiment, the communication device 700 can also include afactory default setting button positioned, for example, below a smallhole in a housing assembly of the communication device 700 to force thecommunication device 700 to re-establish factory settings. In thisembodiment, a user can use a protruding object such as a pen or paperclip tip to reach into the hole and depress the default setting button.The communication device 700 can also include a slot for adding orremoving an identity module such as a Subscriber Identity Module (SIM)card. SIM cards can be used for identifying subscriber services,executing programs, storing subscriber data, and so forth.

The communication device 700 as described herein can operate with moreor less of the circuit components shown in FIG. 7. These variantembodiments can be used in one or more embodiments of the subjectdisclosure.

The communication device 700 can be adapted to perform the functions ofthe user equipment 104 of FIG. 1 and/or the mobile communication devices216 of FIG. 2, the media processor 406, the media devices 408, or theportable communication devices 416 of FIG. 4, as well as the IMS CDs501-502 and PSTN CDs 503-505 of FIG. 5. It will be appreciated that thecommunication device 700 can also represent other devices that canoperate in the communication systems 100, 200 of FIGS. 1 and/or 2,communication systems 400-500 of FIGS. 4-5 such as a gaming console anda media player. In addition, the controller 706 can be adapted invarious embodiments to perform the functions 462-466 and 572-574,respectively.

Upon reviewing the aforementioned embodiments, it would be evident to anartisan with ordinary skill in the art that said embodiments can bemodified, reduced, or enhanced without departing from the scope of theclaims described below. For example, it is understood that in at leastsome instances, the super slice 140 can serve the requesting premiumservice without necessarily utilizing the requesting dedicated slice112, or even any of the dedicated slices 112. For example, the superslice 140 can assume the role of a dedicated slice 112 for at least aduration of the exceptional condition. Other embodiments can be used inthe subject disclosure.

It should be understood that devices described in the exemplaryembodiments can be in communication with each other via various wirelessand/or wired methodologies. The methodologies can be links that aredescribed as coupled, connected and so forth, which can includeunidirectional and/or bidirectional communication over wireless pathsand/or wired paths that utilize one or more of various protocols ormethodologies, where the coupling and/or connection can be direct (e.g.,no intervening processing device) and/or indirect (e.g., an intermediaryprocessing device such as a router).

FIG. 8 depicts an exemplary diagrammatic representation of a machine inthe form of a computer system 800 within which a set of instructions,when executed, may cause the machine to perform any one or more of themethods described above. One or more instances of the machine canoperate, for example, as the NSSF 430, the media processor 406 the mGW132, the SSF 134, the dedicated slices 112, functional modules of thededicated slices 120, 122, 124, 128, the premium function module 114,authentication function modules 142, and other devices of FIGS. 1-2 and4-5. In some embodiments, the machine may be connected (e.g., using anetwork 826) to other machines. In a networked deployment, the machinemay operate in the capacity of a server or a client user machine in aserver-client user network environment, or as a peer machine in apeer-to-peer (or distributed) network environment.

The machine may comprise a server computer, a client user computer, apersonal computer (PC), a tablet, a smart phone, a laptop computer, adesktop computer, a control system, a network router, switch or bridge,or any machine capable of executing a set of instructions (sequential orotherwise) that specify actions to be taken by that machine. It will beunderstood that a communication device of the subject disclosureincludes broadly any electronic device that provides voice, video ordata communication. Further, while a single machine is illustrated, theterm “machine” shall also be taken to include any collection of machinesthat individually or jointly execute a set (or multiple sets) ofinstructions to perform any one or more of the methods discussed herein.

The computer system 800 may include a processor (or controller) 802(e.g., a central processing unit (CPU)), a graphics processing unit(GPU, or both), a main memory 804 and a static memory 806, whichcommunicate with each other via a bus 808. The computer system 800 mayfurther include a display unit 810 (e.g., a liquid crystal display(LCD), a flat panel, or a solid state display). The computer system 800may include an input device 812 (e.g., a keyboard), a cursor controldevice 814 (e.g., a mouse), a disk drive unit 816, a signal generationdevice 818 (e.g., a speaker or remote control) and a network interfacedevice 820. In distributed environments, the embodiments described inthe subject disclosure can be adapted to utilize multiple display units810 controlled by two or more computer systems 800. In thisconfiguration, presentations described by the subject disclosure may inpart be shown in a first of the display units 810, while the remainingportion is presented in a second of the display units 810.

The disk drive unit 816 may include a tangible computer-readable storagemedium 822 on which is stored one or more sets of instructions (e.g.,software 824) embodying any one or more of the methods or functionsdescribed herein, including those methods illustrated above. Theinstructions 824 may also reside, completely or at least partially,within the main memory 804, the static memory 806, and/or within theprocessor 802 during execution thereof by the computer system 800. Themain memory 804 and the processor 802 also may constitute tangiblecomputer-readable storage media.

Dedicated hardware implementations including, but not limited to,application specific integrated circuits, programmable logic arrays andother hardware devices can likewise be constructed to implement themethods described herein. Application specific integrated circuits andprogrammable logic array can use downloadable instructions for executingstate machines and/or circuit configurations to implement embodiments ofthe subject disclosure. Applications that may include the apparatus andsystems of various embodiments broadly include a variety of electronicand computer systems. Some embodiments implement functions in two ormore specific interconnected hardware modules or devices with relatedcontrol and data signals communicated between and through the modules,or as portions of an application-specific integrated circuit. Thus, theexample system is applicable to software, firmware, and hardwareimplementations.

In accordance with various embodiments of the subject disclosure, theoperations or methods described herein are intended for operation assoftware programs or instructions running on or executed by a computerprocessor or other computing device, and which may include other formsof instructions manifested as a state machine implemented with logiccomponents in an application specific integrated circuit or fieldprogrammable gate array. Furthermore, software implementations (e.g.,software programs, instructions, etc.) including, but not limited to,distributed processing or component/object distributed processing,parallel processing, or virtual machine processing can also beconstructed to implement the methods described herein. Distributedprocessing environments can include multiple processors in a singlemachine, single processors in multiple machines, and/or multipleprocessors in multiple machines. It is further noted that a computingdevice such as a processor, a controller, a state machine or othersuitable device for executing instructions to perform operations ormethods may perform such operations directly or indirectly by way of oneor more intermediate devices directed by the computing device.

While the tangible computer-readable storage medium 822 is shown in anexample embodiment to be a single medium, the term “tangiblecomputer-readable storage medium” should be taken to include a singlemedium or multiple media (e.g., a centralized or distributed database,and/or associated caches and servers) that store the one or more sets ofinstructions. The term “tangible computer-readable storage medium” shallalso be taken to include any non-transitory medium that is capable ofstoring or encoding a set of instructions for execution by the machineand that cause the machine to perform any one or more of the methods ofthe subject disclosure. The term “non-transitory” as in a non-transitorycomputer-readable storage includes without limitation memories, drives,devices and anything tangible but not a signal per se.

The term “tangible computer-readable storage medium” shall accordinglybe taken to include, but not be limited to: solid-state memories such asa memory card or other package that houses one or more read-only(non-volatile) memories, random access memories, or other re-writable(volatile) memories, a magneto-optical or optical medium such as a diskor tape, or other tangible media which can be used to store information.Accordingly, the disclosure is considered to include any one or more ofa tangible computer-readable storage medium, as listed herein andincluding art-recognized equivalents and successor media, in which thesoftware implementations herein are stored.

Although the present specification describes components and functionsimplemented in the embodiments with reference to particular standardsand protocols, the disclosure is not limited to such standards andprotocols. Each of the standards for Internet and other packet switchednetwork transmission (e.g., TCP/IP, UDP/IP, HTML, HTTP) representexamples of the state of the art. Such standards are from time-to-timesuperseded by faster or more efficient equivalents having essentiallythe same functions. Wireless standards for device detection (e.g.,RFID), short-range communications (e.g., Bluetooth®, WiFi, Zigbee®), andlong-range communications (e.g., WiMAX, GSM, CDMA, LTE) can be used bycomputer system 800. In one or more embodiments, information regardinguse of services can be generated including services being accessed,media consumption history, user preferences, and so forth. Thisinformation can be obtained by various methods including user input,detecting types of communications (e.g., video content vs. audiocontent), analysis of content streams, and so forth. The generating,obtaining and/or monitoring of this information can be responsive to anauthorization provided by the user. In one or more embodiments, ananalysis of data can be subject to authorization from user(s) associatedwith the data, such as an opt-in, an opt-out, acknowledgementrequirements, notifications, selective authorization based on types ofdata, and so forth.

The illustrations of embodiments described herein are intended toprovide a general understanding of the structure of various embodiments,and they are not intended to serve as a complete description of all theelements and features of apparatus and systems that might make use ofthe structures described herein. Many other embodiments will be apparentto those of skill in the art upon reviewing the above description. Theexemplary embodiments can include combinations of features and/or stepsfrom multiple embodiments. Other embodiments may be utilized and derivedtherefrom, such that structural and logical substitutions and changesmay be made without departing from the scope of this disclosure. Figuresare also merely representational and may not be drawn to scale. Certainproportions thereof may be exaggerated, while others may be minimized.Accordingly, the specification and drawings are to be regarded in anillustrative rather than a restrictive sense.

Although specific embodiments have been illustrated and describedherein, it should be appreciated that any arrangement which achieves thesame or similar purpose may be substituted for the embodiments describedor shown by the subject disclosure. The subject disclosure is intendedto cover any and all adaptations or variations of various embodiments.Combinations of the above embodiments, and other embodiments notspecifically described herein, can be used in the subject disclosure.For instance, one or more features from one or more embodiments can becombined with one or more features of one or more other embodiments. Inone or more embodiments, features that are positively recited can alsobe negatively recited and excluded from the embodiment with or withoutreplacement by another structural and/or functional feature. The stepsor functions described with respect to the embodiments of the subjectdisclosure can be performed in any order. The steps or functionsdescribed with respect to the embodiments of the subject disclosure canbe performed alone or in combination with other steps or functions ofthe subject disclosure, as well as from other embodiments or from othersteps that have not been described in the subject disclosure. Further,more than or less than all of the features described with respect to anembodiment can also be utilized.

Less than all of the steps or functions described with respect to theexemplary processes or methods can also be performed in one or more ofthe exemplary embodiments. Further, the use of numerical terms todescribe a device, component, step or function, such as first, second,third, and so forth, is not intended to describe an order or functionunless expressly stated so. The use of the terms first, second, thirdand so forth, is generally to distinguish between devices, components,steps or functions unless expressly stated otherwise. Additionally, oneor more devices or components described with respect to the exemplaryembodiments can facilitate one or more functions, where the facilitating(e.g., facilitating access or facilitating establishing a connection)can include less than every step needed to perform the function or caninclude all of the steps needed to perform the function.

In one or more embodiments, a processor (which can include a controlleror circuit) has been described that performs various functions. Itshould be understood that the processor can be multiple processors,which can include distributed processors or parallel processors in asingle machine or multiple machines. The processor can be used insupporting a virtual processing environment. The virtual processingenvironment may support one or more virtual machines representingcomputers, servers, or other computing devices. In such virtualmachines, components such as microprocessors and storage devices may bevirtualized or logically represented. The processor can include a statemachine, application specific integrated circuit, and/or programmablegate array including a Field PGA. In one or more embodiments, when aprocessor executes instructions to perform “operations”, this caninclude the processor performing the operations directly and/orfacilitating, directing, or cooperating with another device or componentto perform the operations.

The Abstract of the Disclosure is provided with the understanding thatit will not be used to interpret or limit the scope or meaning of theclaims. In addition, in the foregoing Detailed Description, it can beseen that various features are grouped together in a single embodimentfor the purpose of streamlining the disclosure. This method ofdisclosure is not to be interpreted as reflecting an intention that theclaimed embodiments require more features than are expressly recited ineach claim. Rather, as the following claims reflect, inventive subjectmatter lies in less than all features of a single disclosed embodiment.Thus the following claims are hereby incorporated into the DetailedDescription, with each claim standing on its own as a separately claimedsubject matter.

What is claimed is:
 1. A device, comprising: a processing systemincluding a processor; and a memory that stores executable instructionsthat, when executed by the processing system, facilitate performance ofoperations, comprising: identifying a first group of virtual networkfunctions of a first network slice instantiated within a softwaredefined network and adapted to perform a first activity that facilitatesdelivery of a service to wireless equipment of a first user; detectingan occurrence of a condition; and facilitating, responsive to thedetecting of the occurrence of the condition, access to a second groupof virtual network functions, wherein the second group of virtualnetwork functions when instantiated within a second network slice of thesoftware defined network are configured to deliver the service to thewireless equipment of the first user during the occurrence of thecondition within the first network slice, wherein the second networkslice is further adapted to perform another activity that facilitatesdelivery of another service during an occurrence of another conditionwithin another network slice.
 2. The device of claim 1, wherein thefirst network slice comprises a dedicated network slice of a 3^(rd)Generation Partnership Project (3GPP) 5G network reserved to facilitatedelivery of the service to the wireless equipment of the first user,wherein the dedicated network slice includes the first group of virtualnetwork functions and excludes a virtual network function of the secondgroup of virtual network functions.
 3. The device of claim 2, whereinthe first network slice comprises a reserved network slice of the 3GPP5G network that is not reserved in association with equipment of anyuser.
 4. The device of claim 1, wherein the detecting of the occurrenceof the condition further comprises determining that excess capacity isrequired beyond a capacity of the first group of virtual networkfunctions.
 5. The device of claim 4, wherein the second network slice ofthe software defined network is adapted to perform another activity thatfacilitates delivery of the service, wherein the first group of virtualnetwork functions is incapable of performing the other activity, andwherein the excess capacity comprises one of excess processing capacity,excess storage capacity, excess communication capacity, and anycombination thereof.
 6. The device of claim 1, wherein the facilitatingof the access to the second group of virtual network functions furthercomprises identifying, responsive to the detecting of the occurrence ofthe condition, a reserved network slice comprising the second group ofvirtual network functions, wherein access to the reserved network sliceis not dedicated to equipment of any user.
 7. The device of claim 6,wherein the facilitating of the access to the second group of virtualnetwork functions further comprises initiating, responsive to thedetecting of the occurrence of the condition, a request to temporarilyaccess the reserved network slice.
 8. A method, comprising: determining,by a processing system including a processor, a first group of virtualnetwork functions of a first network slice instantiated within asoftware defined network and adapted to perform a first activity thatfacilitates delivery of a service to wireless equipment of a first user;detecting, by the processing system, an occurrence of a condition; andfacilitating, by the processing system and responsive to the determiningof the occurrence of the condition within the first network slice,access to a second group of virtual network functions, wherein thesecond group of virtual network functions, when instantiated within asecond network slice of the software defined network, are configured todeliver the service to the wireless equipment of the first user duringthe occurrence of the condition within the first network slice, whereinthe second network slice is further adapted to perform another activitythat facilitates delivery of another service during an occurrence ofanother condition within another network slice.
 9. The method of claim8, wherein the first network slice comprises a dedicated network sliceof a 3^(rd) Generation Partnership Project (3GPP) 5G network reserved tofacilitate delivery of the service to the wireless equipment of thefirst user, wherein the dedicated network slice includes the first groupof virtual network functions and excludes a virtual network function ofthe second group of virtual network functions.
 10. The method of claim9, wherein the first network slice comprises a reserved network slice ofthe 3GPP 5G network that is not reserved in association with equipmentof any user.
 11. The method of claim 8, wherein the determining of theoccurrence of the condition further comprises determining, by theprocessing system, that excess capacity is required beyond a capacity ofthe first group of virtual network functions.
 12. The method of claim11, wherein the excess capacity comprises one of excess processingcapacity, excess storage capacity, excess communication capacity, andany combination thereof.
 13. The method of claim 8, wherein thefacilitating of the access to the second group of virtual networkfunctions further comprises identifying, by the processing system andresponsive to the determining of the occurrence of the condition, areserved network slice comprising the second group of virtual networkfunctions, wherein access to the reserved network slice is not dedicatedto equipment of any user.
 14. The method of claim 13, wherein thefacilitating of the access to the second group of virtual networkfunctions further comprises initiating, by the processing system andresponsive to the determining of the occurrence of the condition, arequest to temporarily access the reserved network slice.
 15. Anon-transitory, machine-readable medium, comprising executableinstructions that, when executed by a processing system including aprocessor, facilitate performance of operations, comprising: determininga first group of virtual network functions of a first network sliceinstantiated within a software defined network and adapted to perform afirst activity that facilitates delivery of a service to wirelessequipment of a first user; determining an occurrence of a condition; andfacilitating, responsive to the determining of the occurrence of thecondition within the first network slice, access to a second group ofvirtual network functions of a second network slice, wherein the secondgroup of virtual network functions when instantiated within the softwaredefined network are configured to deliver the service to the wirelessequipment of the first user during the occurrence of the conditionwithin the first network slice, wherein the second network slice isfurther adapted to perform another activity that facilitates delivery ofanother service during an occurrence of another condition within anothernetwork slice.
 16. The non-transitory, machine-readable medium of claim15, wherein the first network slice comprises a dedicated network sliceof a 3^(rd) Generation Partnership Project (3GPP) 5G network reserved tofacilitate delivery of the service to the wireless equipment of thefirst user, wherein the dedicated network slice includes the first groupof virtual network functions and excludes a virtual network function ofthe second group of virtual network functions.
 17. The non-transitory,machine-readable medium of claim 16, wherein the first network slicecomprises a reserved network slice of the 3GPP 5G network that is notreserved in association with equipment of any user.
 18. Thenon-transitory, machine-readable medium of claim 15, wherein thedetermining of the occurrence of the condition further comprisesdetermining, by the processing system, that excess capacity is requiredbeyond a capacity of the first group of virtual network functions. 19.The non-transitory, machine-readable medium of claim 18, wherein theexcess capacity comprises one of excess processing capacity, excessstorage capacity, excess communication capacity, and any combinationthereof.
 20. The non-transitory, machine-readable medium of claim 15,wherein the facilitating of the access to the second group of virtualnetwork functions further comprises identifying, by the processingsystem and responsive to the determining of the condition, a reservednetwork slice comprising the second group of virtual network functions,wherein access to the reserved network slice is not dedicated toequipment of any user.